Fix NU1903 warnings (Lombiq Technologies: OSOE-925)#19167
Merged
Piedone merged 1 commit intoOrchardCMS:mainfrom Apr 18, 2026
Merged
Fix NU1903 warnings (Lombiq Technologies: OSOE-925)#19167Piedone merged 1 commit intoOrchardCMS:mainfrom
Piedone merged 1 commit intoOrchardCMS:mainfrom
Conversation
Member
|
I saw this in VS, but I presume @Piedone created an auto bump for the packages |
Contributor
Author
|
If you mean Renovate, it doesn't look like it has engaged for this one. Maybe because |
Piedone
approved these changes
Apr 18, 2026
Member
|
Yeah, these will be updated following the normal update schedule, which will trigger on Sunday in a few hours. But this is useful to unblock the build due to the warning before that even. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
System.Security.Cryptography.Xml, MailKit and MimeKit trigger security warning errors, such as
System.Security.Cryptography.Xml is referenced indirectly by Microsoft.Identity.Web and Microsoft.AspNetCore.DataProtection.StackExchangeRedis, updating those two automatically pulls it up to the secure patch version, as confirmed with
dotnet nuget why System.Security.Cryptography.Xml.